Integrated hosted directory

ABSTRACT

Methods, systems, and devices for enterprise-wide management of disparate devices, applications, and users are described. A cloud-based central server may maintain an integrated hosted directory, which may allow user authentication, authorization, and management of information technology (IT) resources and/or user account information across device types, operating systems, and software-as-a-service (SaaS) and on-premises applications. User account information for multiple and separate customers may be managed from a single, central directory, and servers may be brought online to allow access to the directory according to system loading.

CROSS REFERENCES

The present application for patent is a continuation of U.S. patent application Ser. No. 16/417,274 by Bhargava et al., entitled “INTEGRATED HOSTED DIRECTORY,” filed May 20, 2019, which is a continuation-in-part of U.S. patent application Ser. No. 16/044,006 by Bhargava et al., entitled “INTEGRATED HOSTED DIRECTORY”, filed Jul. 24, 2018, which is a continuation of U.S. patent application Ser. No. 15/482,522 by Bhargava et al., entitled “INTEGRATED HOSTED DIRECTORY”, filed Apr. 7, 2017, which is a continuation of U.S. patent application Ser. No. 14/728,511 by Bhargava et al., entitled “INTEGRATED HOSTED DIRECTORY”, filed Jun. 2, 2015, each of which is assigned to the assignee hereof, and each of which is expressly incorporated by reference herein in its entirety.

BACKGROUND

Information technology (IT) and networking is increasingly leveraging remote servers and disparate resources. Organizations often rely on internet-based IT infrastructures to serve employees and clients who may be located around the globe. A single enterprise may utilize devices (including laptops, desktops, phones, tablets, printers, etc.) located on premise, within remote data centers, and hosted at remote, third-party owned servers (“the cloud”). Consequently, managing IT infrastructure has become time consuming, labor intensive, and tedious. Additionally, many organizations are relying on a software-as-a-service (SaaS) based model for applications, content, and the like; and as such this SaaS-based model does not lend itself to traditional on-premises management.

While the trend toward cloud and SaaS-based infrastructure has been effective on many fronts, it has introduced a number of challenges related to system administration and user authentication. The disparate nature of servers, devices, applications, and users has given rise to increased networking complexity, security concerns, and poor interoperability of resources. A central means of managing cloud and SaaS resources, and authenticating users for those resources may thus increase the efficiency and productivity of cloud-based IT infrastructure.

SUMMARY

Methods, systems, and devices that support a central directory for enterprise-wide management of disparate devices, applications, and users are described. Within a networked, cloud-based computing system, a central server may maintain an integrated hosted directory, which may allow user authentication, authorization, and management of IT resources and user account information across devices types, operating systems, and SaaS and on-premises applications. Portions of the directory may be shared with or mirrored on various cloud-based and on-premises servers to increase access and usability by system administrators. Furthermore, IT resources for multiple separate customers may be managed from a single, central directory, and servers may be brought online to allow access to the directory according to system loading.

A method of multitenant directory management within a networked computing system, is described. The method may include obtaining user account information at a central server; accessing a multitenant directory at the central server, wherein the multitenant directory comprises a mapping between user identities and the user account information for a plurality of services, wherein each service of the plurality of services is associated with a plurality of users; transmitting at least a first portion of the user account information via the central server, wherein the first portion of the user account information comprises references to a first set of the user account information for a first service of the plurality of services; and providing an indication, via the central server, that a first user of the plurality of users has permission to access the first service based on the transmitted first portion of the user account information.

A central server is described. The central server may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to obtain user account information; access a multitenant directory, wherein the multitenant directory comprises a mapping between user identities and the user account information for a plurality of services, wherein each service of the plurality of services is associated with a plurality of users; transmit at least a first portion of the user account information, wherein the first portion of the user account information comprises references to a first set of the user account information for a first service of the plurality of services; and provide an indication that a first user of the plurality of users has permission to access a first service of the plurality of services based on the transmitted first portion of the user account information.

A central server is described. The central server may include means for obtaining user account information at a central server; means for accessing a multitenant directory at the central server, wherein the multitenant directory comprises a mapping between user identities and the user account information for a plurality of services, wherein each service of the plurality of services is associated with a plurality of users; means for transmitting at least a first portion of the user account information via the central server, wherein the first portion of the user account information comprises references to a first set of the user account information for a first service of the plurality of services; and means for providing an indication, via the central server, that a first user of the plurality of users has permission to access the first service based on the transmitted first portion of the user account information.

Some examples of the method and central servers described herein may include operations, features, means, or instructions for updating the mapping between user identities and the user account information for the plurality of services to associate the first service with the first portion of the user account information.

In some examples of the method and central servers described herein, the first portion of the user account information is associated with a second service prior to associating the first service with the first portion of the user account information.

In some examples of the method and central servers described herein, transmitting at least the first portion of the user account information is based at least in part on updating the mapping.

In some examples of the method and central servers described herein, the user account information comprises one or more of: user name, password, actual name, or user attributes.

Some examples of the method and central servers described herein may include operations, features, means, or instructions for connecting to a first server, wherein transmitting at least the first portion of the user account information is to the first server via the central server.

In some examples of the method and central servers described herein, providing the indication that the first user has permission to access the first service includes transmitting the indication to the first server.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the disclosure are described in reference to the following figures:

FIG. 1 illustrates an exemplary system that supports multitenant directory management in accordance with various aspects of the present disclosure;

FIG. 2 illustrates an example of an integrated hosted directory in a system that supports multitenant directory management in accordance with various aspects of the present disclosure;

FIG. 3 illustrates an example of a web-based console in a system that supports multitenant directory management in accordance with various aspects of the present disclosure;

FIG. 4 illustrates an exemplary process flow in a system that supports multitenant directory management in accordance with various aspects of the present disclosure;

FIG. 5 illustrates an example of a central server that supports multitenant directory management in accordance with various aspects of the present disclosure;

FIG. 6 illustrates an example of an edge server that supports multitenant directory management in accordance with various aspects of the present disclosure; and

FIGS. 7-11 illustrate methods for multitenant directory management in accordance with various aspects of the present disclosure.

DETAILED DESCRIPTION

A central directory for enterprise-wide management of disparate devices, applications, and users and the corresponding user account information may allow IT system administrators to authenticate users across device types, operating systems, on-premises applications, or SaaS-based applications. For instance, users (e.g., organizational employees, user attributes, and the user account information), devices, and applications may be populated into a central store via a web-based console. Permissions may be assigned for all IT resources (e.g., devices, applications, file systems, files, etc.) within consoles, such that once populated, the system administrator may readily manage users, user account information, user attributes and information, and IT resources from a single location. The console may also allow users to manage, through a self-service portal, certain functions—like password resets, profiles, and certificate-based keys—to IT resources to which those users have permissions. The integrated hosted directory may thus reduce management complexity.

Additionally, a single directory may host resources for several different organizations. Unlike traditional or pre-cloud directories, the integrated hosted directory described herein may provide for management of IT resources, users, user account information, user attributes and information, any combination thereof, and so forth, from different customers (e.g., enterprises). This multitenant directory management may allow for selective administration and permission granting between customers. That is, users from one customer may be granted permission to devices, applications, files, and the like, of other customers, providing a simple, seamless way of managing IT resources across organizations. In some examples, user accounts may be created for a customer utilizing user account information and general user information from a different customer.

Aspects of the disclosure are initially described below in the context of a system that supports multitenant directory management. Various examples of an integrated hosted directory and web-based console are then described. These and other aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to multitenant directory management.

FIG. 1 illustrates an exemplary system 100 that supports multitenant directory management in accordance with various aspects of the present disclosure. The system 100 includes a central server 105. The central server 105 may include a directory, such as the integrated hosted directory described herein, that may include IT resources for several different customers. An example of the directory is described in more detail with reference to FIG. 2. As used here, the term customer may refer to an enterprise or organization, rather than an individual. An individual member or element of a customer may be referred to as a user.

The central server 105 may include a directory server, which may host a directory, and which may support access to the directory using, e.g., a particular protocol. In some examples, the directory server supports access to the directory using Lightweight Directory Access Protocol (LDAP). The central server 105 may also include a console server, which may provide a user interface for web-based access to the directory. In some examples, the central server 105 also includes an agent server that controls server agents located on remote devices and may support agent access to the directory.

In some cases, the system 100 includes a number of edge servers 115. Edge servers 115 may be located physically near a customer and physically remote from the central server 105. Edge servers 115 may reflect replicated portions of the central server 105, but their location proximate to a customer may, as compared to an exclusively centralized system, reduce latency, reduce data transmission costs, increase quality of service (QoS), and the like. Moreover, edge servers 115 may be scalable, such that additional servers may be activated (e.g., “spun up”) to accommodate and respond to increases in system loading.

For instance, portions of the directory housed on central server 105 may be reflected (e.g., transmitted) to edge server 115-a after the central server 105 connects to the edge server 115-a. Additionally, or alternatively, portions of the directory housed on central server 105 may be reflected to edge server 115-a in response to edge server 115-a contacting or connecting to central server 105. For some types of resources, users may access the directory, or portion of the directory, at edge server 115-a utilizing the same protocol as the edge server 115-a may use to access the directory at the central server 105. Additionally, or alternatively, users may access the directory, or portion of the directory, at edge server 115-a utilizing a different protocol than the edge server 115-a may use to access the directory at the central server 105. Additionally, or alternatively, users may not access the directory, or portion of the directory, directly at edge server 115-a. Instead, the directory, or portion of the directory provided to edge server 115-a may be used to provision authentication credentials for the user to access a service provided by the edge server 115-a. For example, the directory, or portion of the directory provided to edge server 115-a may include a username and password for a specific user, and that user may then access a service at edge server 115-a using that username and password.

If system loading, as experienced at edge server 115-a, exceeds a threshold, an additional edge server 115-b may be activated. For example, if a number of users attempting access exceeds a preset value or if latency reaches a particular threshold (e.g., a time delay, which may be on the order of tenths or tens of a second), edge server 115-b may be spun up. By way of example, system loading may be based on central processing unit (CPU) usage of edge server 115-a. If a threshold CPU usage exceeds a threshold (e.g., 80 percent of capacity), edge server 115-b may be activated. In other examples, a threshold may be based on memory usage, disk input/output (I/O), a number of customer request, or the like. In such cases, the portions of the directory reflected on edge server 115-a may also be reflected or transmitted to 115-b. If system loading falls below the threshold, or some other threshold value, edge server 115-b may be taken offline. Alternatively, if system loading continues to increase beyond a subsequent threshold, an additional edge server 115-c may be activated, and the portions of the directory may be reflected to it.

In some cases, customers or users may connect directly to an edge server 115-b or 115-c to authenticate with the system 100 and access a portion of the directory hosted on the edge server 115-c or 115-c, or to access a service provided by the edge server 115-b or 115-c using credentials that can be authenticated by the edge server 115-b or 115-c based on the portion of the directory of the central server 105 that has been previously transmitted to edge server 115-b or 115-c. Alternatively, the system 100 may also support certain authentication, authorization, and management on the premises 120 of customers. For example, on-premises (or “on-prem”) server 125-a, which may be physically located on the premises 120-a of a first customer, may include a replica module 130-a. Replica module 130-a may host a portion of the directory with IT resources and user account information of, accessible to, or managed by the first customer. That is, a portion of the directory hosted on central server 105 may be reflected to replica module 130-a. This may be via an edge server 115, in some cases. The devices 126-a may thus, in some examples, be managed by and may be included in the portion of the directory hosted by replica module 130-a. Additionally or alternatively, the devices 126-a may include computing devices of various types (e.g., mobile phones, tablets, notebook computers, desktop computers, servers, etc.), which may utilize various operating systems. Replica module 130-a may thus provide a familiar, local version of the directory, which may be securely maintained and readily accessed by the first customer. As used herein, on-premises may refer to a server, device, or the like that is within the control of the customer. In some cases, this may include servers located in a remote data center owned or controlled by the customer, which may be contrasted with servers maintained or controlled by a third-party and accessible to the customer via the internet (e.g., cloud servers).

Additionally, on-premises server 125-b, which may be physically located on the premises 120-b of a second customer, may include a replica module 130-b. Replica module 130-b may host a portion of the directory with IT resources of, accessible to, or managed by the second customer. Similar to replica module 130-a, a portion of the directory hosted on central server 105 may be reflected to replica module 130-b. But these portions may be different (e.g., include different users, IT resources, user account information, etc.). The devices 126-b may be managed by and may be included in the portion of the directory hosted by replica module 130-b. Additionally or alternatively, the devices 126-b may include computing devices of various types (e.g., mobile phones, tablets, notebook computers, desktop computers, servers, etc.), which may utilize various operating systems

In some cases, system 100 includes a single-sign-on (SSO) server 140. The SSO server 140 may provide access to, or may be represented in the directory. The SSO server 140 may facilitate assertion of a user's identity to a third party using, for instance, an authentication protocol, such as Security Markup Language (SAML), OpenID, OAuth, or the like. Thus, users who have been authenticated at the central server 105 (or an edge server 115, replica module 130, etc.) may gain access to third-party applications, websites, content, or the like, without the necessity of an additional credentialing process. That is, a user authorized by the system 100 may avoid entering login credentials with certain trusted and trusting third parties. In some cases, the SSO server 140 may facilitate access to the central server 105, thus the directory hosted there, without the necessity of further user authentication. For instance, a user authenticated by a trusted third party may gain access to the central server without the necessity of further credentialing.

In some examples, system 100 includes a separate authentication server 145. The authentication server 145 may authenticate users from various customers to the central server 105. For example, a user may access the authentication server with a device, and may authenticate with the authentication server 145. This may involve the user entering a username and password. This authentication process may include the authentication server 145 exchanging a ticket or key with a device of the user. The user may then access the central server 105 or an edge server 115, for instance, based on the authentication with the authentication server 145, which may include the user's device exchanging the ticket or key.

In some examples, the authentication server 145 utilizes Kerberos to facilitate authentication. In some examples, the central server 105 or edge servers 115 may also employ Kerberos.

As mentioned above, aspects of the system 100 may be accessible by and managed through a web-based console 155. The console may include or be a user interface that provides access to maintain a directory, or portions of the directory, hosted on central server 105. As depicted in the example of FIG. 1, the console 155 may provide remote access to the central server 105 via an Internet connection and, for instance, a wireless access point 156. Those skilled in the art will recognize, however, that because central server 105 may be a cloud server, remote access to central server 105 may be achieved in a variety of ways. As discussed in further detail with reference to FIG. 3, the console 155 may allow an IT system administrator to manage user permissions, monitor access to various applications or files, and the like. The console 155 may be or employ a representational state transfer (REST) application programmer interface (API). The REST API may be used to search a directory, query the directory, or provision users for access to the directory via the console 155. Additionally or alternatively, the REST API may be used for authentication to the directory via the console 155.

The system 100 may, in some cases, include access by a device 160 hosting a server agent 165. The device 160 may be any type of computing device, including a server. Server agent 165 may be a software module (e.g., computer- or processor-executable code) that is configured to run certain software on device 160. The server agent 165 may be equipped with various submodules, including those for caching tasks or schedules, storing or registering user encryption certificates, or processing and executing commands. In some examples, the server agent 165 is capable of executing any number of commands or tasks. For instance, the server agent 165 may perform server functions related to user management, disk space management, log monitoring, changing system configurations, sending and receiving emails, or identifying and neutralizing security threats. The central server 105 may allow the server agent 165 to access a directory upon receiving a command via console 155.

In some examples, credentials may be pushed from the central server 105 to the server agent 165. The server agent 165 may be preconfigured to authenticate a user as though the user was directly accessing, or attempting to access, the directory itself. In such cases, when a user authenticates to a device (e.g., console 155) where the server agent 165 is hosted, the server agent 165 may accomplish the authentication independently, providing user access to the directory or to services from the edge server 115 (e.g., using authentication credentials or other account information provided to the edge server 115 from the directory of the central server 105).

In certain examples, system 100 also includes a remote authentication server 170 in communication with an edge server 115. The remote authentication server 170 may authenticate guest users of virtual private network (VPN) users for access to the directory or to services for which account information has been transmitted to the edge server 115 from the directory. For instance, remote authentication server 170 may provide access to a visiting user who connects to the system 100 via wireless access point 175. Additionally or alternatively, remote authentication server 170 may authenticate users from customers described above who are off premises, and are accessing the directory or services via VPN. In some examples, remote authentication server 170 employs Remote Authentication Dial In User Server (RADIUS), or some other protocol that supports authentication, authorization, and accounting. In some examples, the central server 105 or edge servers 115 may also employ RADIUS.

The various elements, components, servers and devices of system 100 may be connected to one another wirelessly or with wired connections. In some cases, they are connected via the Internet. Communication between the various devices may utilize Transport Layer Security (TLS), Secure Sockets Layer (SSL), or some other security or encryption protocol. As used herein, the term server refers to a computer or program in a network that provides services, including access to applications, files, peripherals, etc., to other computers or programs, or consoles within a network. As discussed below, this may include both software and hardware, and real and virtual machines. In some examples, a server is a computer program that operates to support or perform tasks on behalf of other programs, computers, or users. Further, as used herein, a server may include a “rack” or enclosure housing computer hardware and software.

The system 100 may thus support multitenant directory management. This may be accomplished, in part, with an integrated hosted directory on central server 105, which may facilitate authentication, authorization, and management of IT resources across devices types, operating systems, and SaaS and on-premises applications. The integrated hosted directory on central server 105, may further facilitate the management of user account information across device types, operating systems, applications, and organizations.

FIG. 2 illustrates an example 200 of an integrated hosted directory 202 in a system, such as system 100 of FIG. 1, that supports multitenant directory management in accordance with various aspects of the present disclosure. The directory 202 may be stored in a directory server (or directory server module) 205 of a central server 105-a, which may be an example of the central server 105 of FIG. 1. The directory 202 may be a system, such as a software system, that maps, organizes, and connects users to IT resources, including servers, devices, peripherals, applications, file systems, files, and the like. In some cases, the directory 202 may be referred to as a directory service. The directory 202 provides a system for allowing and maintaining records of which users are or should be allowed to access what IT resources, and whether, when, and by whom those IT resource were accessed.

The example of FIG. 2 illustrates one depiction of a directory 202. The directory 202 may include fields or modules representative of users 210 and IT resources or user account information. The IT resources may include file system 215, devices 220, files 230, and instances 235, and the user account information may include user-specific information such as user name, password, certification keys, actual name, or one or more user attributes (e.g., home address, phone number, demographic and geographic attributes, etc.). The directory 202 may thus include a reference or references to the IT resources or the user account information. Additionally or alternatively, the directory may be said to reference IT resources. For example, the users 210 may be users associated with one or several customers. The directory 202 may provide a mapping to a file system 215 (or file systems) to which users 210 have access. The file system 215 may, in some cases represent applications, such as SaaS applications. The users 210 may also be mapped to certain devices 220, which may be mapped to certain files 230 to which a user 210 or devices 220, or both, has permissions. The devices 220 may be representative of devices 126 of FIG. 1. The files 230 may be mapped to instances 235, which may provide details or information relevant to managing access by users 210.

In some examples, the directory may include a mapping between user identities and/or the user account information for one or more organizations. The user account information may be created using the server agent of FIG. 1 and may be stored in the directory on the central server 105. Alternatively, the user account information may be imported from another service or program. The user account information may be provisioned to other servers (e.g., edge servers) from the central server 105. In some examples, the user account information may be created and/or generated inside of a first application and may additionally be created inside of a second application using the user account information of the first application.

The directory 202 includes an arbitrary set of fields and modules for purposes of illustration. Those skilled in the art will recognize that a directory may take on a number of forms and may include fields different from those illustrated here.

FIG. 3 illustrates an example 300 of a web-based console 155-a in a system, such as system 100 of FIG. 1, that supports multitenant directory management in accordance with various aspects of the present disclosure. The console 155-a may include a user interface (UI) 305, which may provide a portal for access to a directory, such as directory 202 of FIG. 2.

The UI 305 may include fields 310, icons, and the like that allow a user to interact with the directory 202. The fields 310 may correspond or be associated with some or all of the IT resources (file system 215, device 220, files 230, and instances 235) of or referenced by the directory 202. That is, a system administrator may, for example, navigate, identify, and manage the mapping of users to IT resources via the UI 305. In some examples, the UI may include user account information (not depicted in FIG. 3, such as user name, password, the actual name, or one or more user attributes (e.g., including home address, phone number, demographic and geographic attributes, etc.).

The UI 305 may provide real-time information about user interactions with the directory via window 315. For instance, the window 315 may display information about a particular user's permissions to access various IT resources. In some cases, the window 315 may also provide information about current and historic uses of such IT resources. Various devices, applications, security issues, and the like, related to a particular user may thus be monitored and managed via UI 305.

FIG. 4 illustrates an exemplary process flow 400 in a system, such as system 100 of FIG. 1, that supports multitenant directory management in accordance with various aspects of the present disclosure. The process flow 400 may include a central server 105-b, servers 115-d and 115-e, an authentication server 145-a, on-premises server 125-c, console 155-b, SSO server 140-b, a remote (e.g., server-agent hosting) device 160-a, and users 405. Each of these may examples of corresponding devices, entities, and the like, described with reference to FIGS. 1-3.

At 410, a directory at a central server 105-b may be accessed. The directory may be as described with reference to FIG. 2, and may include IT resources for a plurality of customers, such as customers having users 405.

Additionally, or alternatively, the directory may include user account information for one or more users 405, as described herein. In some examples, the multitenant directory may include a mapping between user identities and the user account information for a plurality of organizations. For example, the multitenant directory may store a central repository of user information, and may map user identities to one or more organizations or services. Each mapping between a user identity and one of the organizations or services, may include or indicate a subset of the user account information for that user identity that is accessible to or required by the service or organization. In some examples, at least a portion of the user account information for a user identity may be obtained from user account information created for a different service or organization, and a portion of that user account information may be shared with or accessible to another service or organization via the mapping in the directory of the central server 105-b in accordance with appropriate permissions and access controls.

For example, a set of employee users at a company may have individual accounts set up for a service, such as Microsoft Office 365, and each of those users may have an associated username, password, photo, and real name associated with their Office 365 account. This user account information for the Office 365 account associated with each user may be imported to, stored, or maintained in the directory, which may be operated by or accessible to the company. Thus, the directory may store a mapping of each user identity of an employee user to the username, password, photo, and real name of that user. The directory may add a mapping of this user account information to the Office 365 service, which may indicate that this account information is applicable to or used by the Office 365 service. The

Office 365 service may use this user account information to authenticate each user for access to the service. A representative of the company may wish to create or update user accounts on a different service, such as Google GSuite, for each of the employee users based on the account information already used for Office 365. Doing so may allow for more streamlined management of the different services and a more consistent experience for the users across both services. To make the user account information mapped to Office 365 also available to or accessible by the GSuite service, the mapping for each user identity in the directory may be updated to further associate the username, password, photo, and real name of each user with the Google GSuite service.

At 415, the central server 105-b may connect to or activate a first server 115-e and, at 420, a first portion of the user account information in the directory may be transmitted from the central server 105-b to a first server 115-d. In some examples, the central server 105-b may connect to or activate the first server 115-d. The first server 115-d may be managed or operated by an organization referenced in the access directory, such as an organization that owns, manages, or subscribes to services offered by the central server 105-b. In some cases the first server 115-d may be owned by an enterprise that receives account information for users from central server 105-b and uses that account information to provide those users access to a service. Continuing the example above, the first server 115-d may provide or facilitate the Google GSuite service to employee users, and as part of the process of creating Google GSuite accounts for the employee users, and the first portion of the user account information in the directory may include the user name, password, real name, and photo of a first set of one or more employee users for which the GSuite account is to be created or updated. This user account information provided by the central server 105-b to the first server 115-d may be used to establish, maintain, or update a corresponding GSuite account by or at the first server 115-d for each employee user associated with the first portion of the user account information transmitted to the first server 115-d.

Additionally, or alternatively, the first portion of the directory may include IT resources for a first customer of the plurality of customers as described with reference to FIGS. 1-3.

At 425, a second portion of the directory from the central server 105-b may be transmitted to the first server 115-d. The second portion of the directory may include the user account information for a second set of one or more users of the plurality of users.

Continuing the example above, the second portion of the directory may include the user name, password, real name, and photo of a second set of one or more employee users for which the GSuite account is to be created or updated. This user account information provided by the central server 105-b to the first server 115-d may be used to establish, maintain, or update a corresponding GSuite account by or at the first server 115-d for each employee user associated with the second portion of the user account information transmitted to the first server 115-d.

Additionally, or alternatively, the second portion of the directory may include IT resources for the second set of one or more users of the plurality of users as described above with reference to FIGS. 1-3.

At 430, a second server 115-e may be connected to or be activated based, for instance, on a system load from the plurality of users. In some examples, the central server 105-b may connect to the second server 115-e and then the second server 115-e may be activated. For instance, the system load may exceed a threshold, as described above with reference to FIG. 1. At 435 the first portion of the directory may be transmitted from the central server 105-b to the second server 115-e, and at 440 the second portion of the directory may be transmitted from the central server 105-b to the second server 115-e. In some examples, the first server 115-d and the second server 115-e may be examples of edge servers described herein.

In some examples, the central server 105-b may provide an indication to the first server 115-d or the second server 115-e when changes or updates to mappings occur in the directory or associated access permissions associated with the user identities. Continuing the above example, upon updating the mapping of the user identities associated with employee users to expose the user name, password, actual name, and photo associated with each user identity to the GSuite service, the central server 105-b may transmit a message to the first server 115-d or the second server 115-e containing the user name, password, actual name, and photo associated with the user identities of the employee users in the directory for use by the GSuite service. In some examples, this message may also include an indication of a protocol to be used by a user of the first server 115-d or the second server 115-e to access this account information. Additionally, or alternatively, the central server 105-b may provide an indication to the first server 115-d or the second server 115-e that one or more users have permission to access a service based on the user account information transmitted to the server 115-d or 115-e at 420 or 425 and associated with that service.

At 445, a user 405 may be authenticated for access to a first service at the first server 115-d or the second server 115-e utilizing a first protocol. The user 405 may attempt to access a web-based application using a device, for example, and the directory may provide a mapping of that user's permission for such access to the first service and the user account information to be received to authenticate the user 405. At 450, the same or a different user 405 may be authenticated for access to a second service at the first server 115-d or the second server 115-e utilizing the first protocol. Continuing the above example, the first service and the second service may be web services provided to employee users, such as Office 365 or GSuite.

At 455, a user 405 may be authenticated for access to the first service or a second service or service utilizing a second protocol that is different from the first protocol. This may include, at 460, the user 405 accessing a remote authentication server 145-a, which may communicate with one of the servers 115-d or 115-e, or the central server 105 to facilitate authentication. In some examples, the first protocol is LDAP and the second protocol is Kerberos.

At 465, the central server 105-b may identify a command received via web-based console 155-b and, at 470, the central server 105-b may receive a request for access to a service or computer system from a server agent located on a remote device 160-a. The central server 105-b may, in response at 475, transmit data to the server agent on remote device160-a in response to the request for access.

At 480, the central server 105-b may be in communication with the SSO server 140-a to support identity assertion to a third party on behalf of a user. As described above, the identity assertion may be on the SSO server 140-b accessing the directory on the central server 105-b, and the SSO server 140-a may utilize at least one of SAML, OpenID, or OAuth.

FIG. 5 illustrates an example 500 of a central server 105-c that supports multitenant directory management in accordance with various aspects of the present disclosure. The central server 105-c may be an example of central server 105 described with reference to FIGS. 1-4, and may include a directory server module 205-a, a console server module 510, and an agent server module 515.

The directory server module 205-a may be an example of the directory server module 205 of FIG. 2 and may host a directory 202 (FIG. 2). Some or all of the directory may be accessible to other components of the central server 105-b. The directory server module 205-a may, in some cases and in combination with other components of the central server 105-c, access the directory, transmit portions of the directory, and authentication users for access to the directory, as described with reference to FIGS. 1 and 4.

The console server module 510 may, in combination with other components of the central server 105-c, identify a command received via a web-based console, as described with reference to FIGS. 1 and 4. In some cases, the console server module 510 facilitates the operations described with reference to FIG. 3.

The agent server module 515 may cause the central server 105-c to receive a request for directory access from a server agent located on a remote device. In some cases, the agent server module 515, in combination with other components of the central server 105-c, may transmit data to the server agent in response to the request for directory access and based on the identified command, as described with reference to FIGS. 1-3.

The account information server module 545 may cause the central server 105-c to obtain user account information, access a multitenant directory including a mapping between user identities and the user account information for a plurality of organizations, transmit at least a first portion of the user account information including references to a first set of the user account information for a first organization of the plurality of organizations, and provide an indication that a first user has permission to access a first service based on the transmitted first portion of the user account information.

The central server 105-c may include a processor 520, memory 525 (including software/firmware (SW) 530), and a network communications module 535. The various modules of the central server 105-c may be in communication via one or more buses 540. The network communications module 535 may be configured for secure, bi-directional communication with other devices, servers, and the like in a system, such as system 100 of FIG. 1, via one or more wired or wireless links. For example, the network communications module 535 may include a modem configured to modulate packets and transmit them to, and to demodulate received packets.

The memory 525 may include random access memory (RAM) and read only memory (ROM). The memory 525 may store computer-readable, computer-executable software/firmware code 530, including instructions that, when executed, cause the processor 520 to perform various functions described herein (e.g., facilitating multitenant directory management.). Alternatively, the software/firmware code 530 may not be directly executable by the processor 520 but cause a computer (e.g., when compiled and executed) to perform functions described herein. The processor 520 may include an intelligent hardware device, (e.g., a central processing unit (CPU), a microcontroller, an ASIC, etc.).

FIG. 6 illustrates an example 600 of a server 115-f that supports multitenant directory management in accordance with various aspects of the present disclosure. The server 115-f may be an example of an edge server 115 described with reference to FIGS. 1-3 or a server 115-d or 115-e described with reference to FIG. 4, and may include a first customer directory module 605, a second customer directory module 610, and an nth customer directory module 615.

The first customer directory module 605 and the second customer directory module 610 may receive, host, and provide authenticated access to first and second portions of a directory, respectively, from a central server 105, as described with reference to FIGS. 1-5. The preceding description has generally discussed a first and second portion of the directory for first and second customers. Additional customers may be supported by the directory (e.g., 202 of FIG. 2). Thus, in some cases, an nth customer directory module may receive, host, and provide authenticated access to an nth portion of the directory from a central server 105.

The server 115-f may include a processor 620, memory 625 (including software/firmware (SW) 630), and a network communications module 635. The various modules of the server 115-f may be in communication via one or more buses 640. The network communications module 635 may be configured for secure, bi-directional communication with other devices, servers, and the like in a system, such as system 100 of FIG. 1, via one or more wired or wireless links. For example, the network communications module 635 may include a modem configured to modulate packets and transmit them to, and to demodulate received packets.

The memory 625 may include random access memory (RAM) and read only memory (ROM). The memory 625 may store computer-readable, computer-executable software/firmware code 630, including instructions that, when executed, cause the processor 620 to perform various functions described herein (e.g., facilitating multitenant directory management.). Alternatively, the software/firmware code 630 may not be directly executable by the processor 620 but cause a computer (e.g., when compiled and executed) to perform functions described herein. The processor 620 may include an intelligent hardware device, (e.g., a central processing unit (CPU), a microcontroller, an ASIC, etc.)

The components of central server 105-c and server 115-f may each, individually or collectively, be implemented with at least one ASIC adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on at least one IC. In other examples, other types of integrated circuits may be used (e.g., Structured/Platform ASICs, an FPGA, or another semi-custom IC), which may be programmed in any manner known in the art. The functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.

FIG. 7 illustrates a method 700 for multitenant directory management in accordance with various aspects of the present disclosure. The operations of method 700 may be implemented by various servers and devices within a system, as described with reference to FIGS. 1-6. In some examples, one or more servers, such as central server 105, may execute a set of codes to control the functional elements of servers and devices with the system 100 to perform the functions described below. Additionally or alternatively, the central server 105 may perform aspects the functions described below using special-purpose hardware.

At block 705, the central server 105 may access a directory at the central server, where the directory may include user account information for a plurality of customers as described with reference to FIGS. 1-4. In some examples, the directory may include IT resources or user account information. In certain examples, the operations of block 705 may be performed by the directory server module 205 as described with reference to FIGS. 2 and 5.

At block 710, the central server 105 may connect to a first edge server of the plurality of edge servers as described with reference to FIGS. 1-4. In some examples, the central server 105 may connect to the first edge server and then may activate the first edge server. In certain examples, the operations of block 710 may be performed by the directory server module 205 as described with reference to FIG. 5.

At block 715, the central server 105 may transmit a first portion of the directory from the central server to the first edge server, where the first portion of the directory includes user account information for a first customer of the plurality of customers as described with reference to FIGS. 1-4. In some examples, the first portion of the directory may include IT resources or user account information. In certain examples, the operations of block 715 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 720, the central server 105 may transmit a second portion of the directory from the central server to the first edge server, where the second portion of the directory may include user account information for a second customer of the plurality of customers as described with reference to FIGS. 1-4. In some examples, the second portion of the directory may include IT resources or user account information. In certain examples, the operations of block 720 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 725, the central server 105 may connect to a second edge server of the plurality of edge servers based at least in part on a system load from the plurality of customers as described with reference to FIGS. 1-4. In some examples, the central server 105 may connect to the second edge server and then nay activate the second edge server. In certain examples, the operations of block 725 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 730, the central server 105 may transmit the first and second portions of the directory to the second edge server as described in FIGS. 1-4. In certain examples, the operations of block 730 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 735, the central server 105 or one or more edge servers 115 may authenticate a first user for access to the first portion of the directory at the first and second edge servers utilizing a first protocol as described with reference to FIGS. 1-4. In certain examples, the operations of block 735 may be performed by the directory server module 205 as described with reference to FIG. 5.

FIG. 8 illustrates a method 800 for multitenant directory management in accordance with various aspects of the present disclosure. The operations of method 800 may be implemented by various servers and devices within a system, as described with reference to FIGS. 1-6. In some examples, one or more servers, such as central server 105, may execute a set of codes to control the functional elements of servers and devices with the system 100 to perform the functions described below. Additionally or alternatively, the central server 105 may perform aspects the functions described below using special-purpose hardware. The method 800 may also incorporate aspects of method 700 of FIG. 7.

At block 805, the central server 105 may access a directory at the central server, where the directory may include IT resources and/or user account information for a plurality of customers as described with reference to FIGS. 1-4. In certain examples, the operations of block 805 may be performed by the directory server module 205 as described with reference to FIGS. 2 and 5.

At block 810, the central server 105 may connect to a first edge server of the plurality of edge servers as described with reference to FIGS. 1-4. In some examples, the central server 105 may connect to the first edge server and then may activate the first edge server. In certain examples, the operations of block 810 may be performed by the directory server module 205 as described with reference to FIG. 5.

At block 815, the central server 105 may transmit a first portion of the directory from the central server to the first edge server, where the first portion of the directory includes IT resources or may include user account information for a first customer of the plurality of customers as described with reference to FIGS. 1-4. In certain examples, the operations of block 815 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 820, the central server 105 may transmit a second portion of the directory from the central server to the first edge server, where the second portion of the directory may include IT resources and/or user account information for a second customer of the plurality of customers as described with reference to FIGS. 1-4. In certain examples, the operations of block 820 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 825, the central server 105 may connect to a second edge server of the plurality of edge servers based at least in part on a system load from the plurality of customers as described with reference to FIGS. 1-4. In some examples, the central server 105 may connect to the second edge server and then may activate the second edge server. In certain examples, the operations of block 825 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 830, the central server 105 may transmit the first and second portions of the directory to the second edge server as described in FIGS. 1-4. In certain examples, the operations of block 830 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 835, the central server 105 or one or more edge servers 115 may authenticate a first user for access to the first portion of the directory at the first and second edge servers utilizing a first protocol as described with reference to FIGS. 1-4. In certain examples, the operations of block 835 may be performed by the directory server module 205 as described with reference to FIG. 5.

At block 840, the central server 105 may identify a command received via a web-based console as described with reference to FIGS. 1 and 4. In certain examples, the operations of block 840 may be performed by the console server module 510 as described with reference to FIG. 5.

At block 845, the central server 105 may receive a request for directory access from a server agent located on a remote device as describe with reference to FIGS. 1 and 4. In certain examples, the operations of block 845 may be performed by the agent server module 515 as described with reference to FIG. 5.

At block 850, the central server 105 may transmit data to the server agent in response to the request for directory access based at least in part on the identified command as described with reference to FIGS. 1 and 4. In certain examples, the operations of block 850 may be performed by the agent server module 515 as described with reference to FIG. 5.

FIG. 9 illustrates a method 900 for multitenant directory management in accordance with various aspects of the present disclosure. The operations of method 900 may be implemented by various servers and devices within a system, as described with reference to FIGS. 1-6. In some examples, one or more servers, such as central server 105, may execute a set of codes to control the functional elements of servers and devices with the system 100 to perform the functions described below. Additionally or alternatively, the central server 105 may perform aspects the functions described below using special-purpose hardware. The method 900 may also incorporate aspects of methods 700 and 800 of FIGS. 7 and 8.

At block 905, the central server 105 may access a directory at the central server, where the directory may include IT resources and/or user account information for a plurality of customers as described with reference to FIGS. 1-4. In certain examples, the operations of block 905 may be performed by the directory server module 205 as described with reference to FIGS. 2 and 5.

At block 910, the central server 105 may connect to a first edge server of the plurality of edge servers as described with reference to FIGS. 1-4. In some examples, the central server 105 may connect to the first edge server and then may activate the first edge server. In certain examples, the operations of block 910 may be performed by the directory server module 205 as described with reference to FIG. 5.

At block 915, the central server 105 may transmit a first portion of the directory from the central server to the first edge server, where the first portion of the directory includes IT resources for a first customer of the plurality of customers as described with reference to FIGS. 1-4. In certain examples, the operations of block 915 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 920, the central server 105 may transmit a second portion of the directory from the central server to the first edge server, where the second portion of the directory may include IT resources and/or user account information for a second customer of the plurality of customers as described with reference to FIGS. 1-4. In certain examples, the operations of block 920 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 925, the central server 105 may connect to a second edge server of the plurality of edge servers based at least in part on a system load from the plurality of customers as described with reference to FIGS. 1-4. In some examples, the central server 105 may connect to the second edge server and then may activate the second edge server. In certain examples, the operations of block 925 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 930, the central server 105 may transmit the first and second portions of the directory to the second edge server as described in FIGS. 1-4. In certain examples, the operations of block 930 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 935, the central server 105 or one or more edge servers 115 may authenticate a first user for access to the first portion of the directory at the first and second edge servers utilizing a first protocol as described with reference to FIGS. 1-4. In certain examples, the operations of block 935 may be performed by the directory server module 205 as described with reference to FIG. 5.

At block 940, the central server 105 may authenticate a second user for access to the second portion of the directory at the first edge and second edge servers utilizing the first protocol as described with reference to FIGS. 1-4. In certain examples, the operations of block 940 may be performed by the directory server module 205 as described with reference to FIG. 5.

At block 945, the central server 105 or the authentication server 145, or both, may authenticate a third user for access to the first or second portion of the directory utilizing a second protocol that is different from the first protocol as described with reference to FIGS. 1 and 4. In certain examples, the operations of block 945 may be performed by the directory server module 205 as described with reference to FIG. 5.

At block 950, the central server 105 may communicate with an authentication server that supports authentication using the second protocol, where the third user may be authenticated via a request to the authentication server as described with reference to FIGS. 1 and 4. In certain examples, the operations of block 950 may be performed by the network communications module 535 as described with reference to FIG. 5.

FIG. 10 illustrates a method 1000 for multitenant directory management in accordance with various aspects of the present disclosure. The operations of method 1000 may be implemented by various servers and devices within a system, as described with reference to FIGS. 1-6. In some examples, one or more servers, such as central server 105, may execute a set of codes to control the functional elements of servers and devices with the system 100 to perform the functions described below. Additionally or alternatively, the central server 105 may perform aspects the functions described below using special-purpose hardware. The method 1000 may also incorporate aspects of methods 700, 800, and 900 of FIGS. 7, 8, and 9.

At block 1005, the central server 105 may access a directory at the central server, where the directory may include IT resources and/or user account information for a plurality of customers as described with reference to FIGS. 1-4. In certain examples, the operations of block 1005 may be performed by the directory server module 205 as described with reference to FIGS. 2 and 5.

At block 1010, the central server 105 may connect to a first edge server of the plurality of edge servers as described with reference to FIGS. 1-4. In some examples, the central server 105 may connect to the first edge server and then may activate the first edge server. In certain examples, the operations of block 1010 may be performed by the directory server module 205 as described with reference to FIG. 5.

At block 1015, the central server 105 may transmit a first portion of the directory from the central server to the first edge server, where the first portion of the directory includes IT resources and/or user account information for a first customer of the plurality of customers as described with reference to FIGS. 1-4. In certain examples, the operations of block 1015 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 1020, the central server 105 may transmit a second portion of the directory from the central server to the first edge server, where the second portion of the directory may include IT resources and/or user account information for a second customer of the plurality of customers as described with reference to FIGS. 1-4. In certain examples, the operations of block 1020 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 1025, the central server 105 may connect to a second edge server of the plurality of edge servers based at least in part on a system load from the plurality of customers as described with reference to FIGS. 1-4. In some examples, the central server 105 may connect to the second edge server and then may activate the second edge server. In certain examples, the operations of block 1025 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 1030, the central server 105 may transmit the first and second portions of the directory to the second edge server as described in FIGS. 1-4. In certain examples, the operations of block 1030 may be performed by the directory server module 205 or network communications module 535 as described with reference to FIG. 5.

At block 1035, the central server 105 or one or more edge servers 115 may authenticate a first user for access to the first portion of the directory at the first and second edge servers utilizing a first protocol as described with reference to FIGS. 1-4. In certain examples, the operations of block 1035 may be performed by the directory server module 205 as described with reference to FIG. 5.

At block 1040, the central server 105 and one or more edge servers 115 may transmit the first portion of the directory from the first edge server to a portion of an on-premises server of the first customer as described in FIGS. 1 and 4. In certain examples, the operations of block 1040 may be performed by the directory server module 205 and the network communications module 535 as described with reference to FIG. 5, or the first customer directory module 605 and the network communications module 635 as describe with reference to FIG. 6.

At block 1045, the central server 105 may communicate with a single-sign-on server to support identity assertion to a third party on behalf of a customer of the plurality of customers as described with reference to FIGS. 1 and 4. The identity assertion may be based at least in part on the single-sign-on server accessing the directory. In certain examples, the operations of block 1040 may be performed by the directory server module 205 and the network communications module 535 as described with reference to FIG. 5.

FIG. 11 illustrates a method 1100 for multitenant directory management in accordance with various aspects of the present disclosure. The operations of method 1100 may be implemented by various servers and devices within a system, as described with reference to FIGS. 1-6. In some examples, one or more servers, such as central server 105, may execute a set of codes to control the functional elements of servers and devices with the system 100 to perform the functions described below. Additionally or alternatively, the central server 105 may perform aspects the functions described below using special-purpose hardware. The method 1100 may also incorporate aspects of methods 700, 800, and 900 of FIGS. 7, 8, and 9.

At block 1105, the central server may obtain user account information. The user account information may be received by the central server from another device over a network connection, or input to the central server in connection with the creation or maintenance of a user account with a service or organization.

At block 1110, the central server may access a multitenant directory containing a mapping between user identities and the user account information for a plurality of services. Each of the services may be associated with a plurality of users.

At block 1115, the central server transmits at least a first portion of the user account information to a recipient, such as another server. The first portion of the user account information may include references to a first set of the user account information for a first service of the plurality of services.

At block 1120, the central server may provide an indication, such as to the other server, that a first user of the plurality of users has permission to access the first service based on the transmitted first portion of the user account information.

Thus, methods 700, 800, 900 and 1000 may provide for multitenant directory management, which may utilize an integrated hosted directory or a centralized mapping of user account information to different services. It should be noted that methods 700, 800, 900 and 1000 describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified such that other implementations are possible. In some examples, aspects from two or more of the methods 700, 800, 900 and 1000 may be combined.

The description herein provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure.

Various examples may omit, substitute, or add various procedures or components as appropriate. Also, features described with respect to some examples may be combined in other examples.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “exemplary” as may be used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a digital signal processor (DSP) and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Also, as used herein, including in the claims, “or” as used in a list of items (for example, a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can comprise RAM,

ROM, electrically erasable programmable read only memory (EEPROM), compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

The description herein is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein. 

What is claimed is:
 1. A method of multitenant directory management, comprising: accessing a multitenant directory that comprises, for a plurality of services, references to corresponding portions of account information for corresponding sets of users, the multitenant directory comprising, for a first service of the plurality of services, a first reference to a first portion of account information for a set of users; updating the references at the multitenant directory, wherein the multitenant directory comprises, for a second service of the plurality of services, a second reference to a second portion of the account information for the set of users based on the updating; transmitting, based on updating the references at the multitenant directory, the second reference to the second portion of the account information associated with the second service; and providing an indication that the set of users has permission to access the second service based on transmitting the second reference.
 2. The method of claim 1, further comprising: receiving a request to associate, for the set of users, the second service with the second portion of the account information, wherein the references at the multitenant directory are updated based on receiving the request.
 3. The method of claim 1, wherein: the second reference to the second portion of the account information is transmitted to an endpoint, and the indication is provided to the endpoint.
 4. The method of claim 3, wherein the endpoint comprises a device, a computer, a server, an application, a virtual machine, or any combination thereof.
 5. The method of claim 1, wherein: the first portion of the account information for the set of users is accessible to the first service, and the second portion of the account information for the set of users is accessible to the second service.
 6. The method of claim 1, wherein: the first portion of the account information comprises a third portion of the account information that is restricted for the second service.
 7. The method of claim 1, wherein the second portion of the account information for the set of users is the same as the first portion of the account information for the set of users.
 8. The method of claim 1, wherein the first portion of the account information for the set of users and the second portion of the account information for the set of users comprise overlapping account information.
 9. The method of claim 1, wherein the account information for the set of users comprises a username, password, certification keys, photo, actual name, home address, phone number, demographic attributes, geographic attributes, a security protocol, or any combination thereof.
 10. The method of claim 1, further comprising: obtaining the account information for a plurality of users comprising the set of users; and storing the account information for the plurality of users.
 11. The method of claim 10, further comprising: determining, for the plurality of services, the references to the corresponding portions of the account information for the corresponding sets of users.
 12. A method of multitenant directory management, comprising: obtaining, at a central server, account information for a user, wherein the account information is for a first service of a plurality of services; storing, in a multitenant directory and for the first service, a first reference to the account information based on obtaining the account information; generating, in the multitenant directory and for a second service of the plurality of services, a second reference to a portion of the account information that was obtained for the user for the first service, the portion of the account information being accessible to the second service; transmitting, based on the generating, the second reference to the portion of the account information that is accessible to the second service; and providing, an indication that the user has permission to access the second service based on transmitting the second reference.
 13. The method of claim 12, further comprising: receiving, from the first service, a request to authenticate the user; and authenticating the user based at least in part on the account information.
 14. The method of claim 12, further comprising: receiving a request to create, for the second service, an account for the user; and updating the multitenant directory based at least in part on receiving the request, wherein the second reference is generated based at least in part on updating the multitenant directory.
 15. The method of claim 14, further comprising: transmitting a second indication that the multitenant directory has been updated.
 16. The method of claim 12, wherein: the second reference is transmitted to an endpoint, the endpoint comprising a device, a computer, a server, an application, a virtual machine, or any combination thereof, and the indication is provided to the endpoint.
 17. The method of claim 12, further comprising: updating the multitenant directory based at least in part on a change to the account information; and transmitting an indication that the portion of the account information has been updated based at least in part on updating the multitenant directory.
 18. A central server, comprising: a processor; and a memory coupled with the processor, the memory storing code that is executable by the processor to: access a multitenant directory that comprises, for a plurality of services, references to corresponding portions of account information for corresponding sets of users, the multitenant directory comprising, for a first service of the plurality of services, a first reference to a first portion of account information for a set of users; update the references at the multitenant directory, wherein the multitenant directory comprises, for a second service of the plurality of services, a second reference to second portion of the account information for the set of users based on the updating; transmit, based on updating the multitenant directory, the second reference to the second portion of the account information associated with the second service; and provide an indication that the set of users has permission to access the second service based on transmitting the second reference.
 19. The central server of claim 18, wherein the code is further executable by the processor to: receive a request to associate, for the set of users, the second service with the second portion of the account information, wherein the references at the multitenant directory are updated based on receiving the request.
 20. The central server of claim 18, wherein the code is further executable by the processor to: obtain the account information for a plurality of users comprising the set of users; and store the account information for the plurality of users. 